Skip to content

profile: preserve inline frame columns in location merge keys - #1016

Open
cuishuang wants to merge 1 commit into
google:mainfrom
cuishuang:fix-profile-bug
Open

profile: preserve inline frame columns in location merge keys#1016
cuishuang wants to merge 1 commit into
google:mainfrom
cuishuang:fix-profile-bug

Conversation

@cuishuang

Copy link
Copy Markdown
Contributor

The location merge key allocates three fields per inline frame (function, line, and column), but indexes each frame using a stride of two. As a result, the function ID of a later inline frame overwrites the column of the preceding frame.

For example, locations that differ only in the column of a non-terminal inline frame can be incorrectly merged, causing samples from distinct source locations to be aggregated together.

Use a stride of three when encoding function IDs, line numbers, and column numbers in the location key.

@aalexand
aalexand enabled auto-merge (squash) August 23, 2026 23:58
@codecov-commenter

codecov-commenter commented Aug 24, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 67.35%. Comparing base (ef3492d) to head (85ce5af).

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1016   +/-   ##
=======================================
  Coverage   67.35%   67.35%           
=======================================
  Files          44       44           
  Lines        7793     7793           
=======================================
  Hits         5249     5249           
  Misses       2112     2112           
  Partials      432      432           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants